reminds MCP

Created By
Jason Wooa year ago
一款可以用来记录reminds 闪念的MCP Server reminds 是一款为终身学习者量身打造的 AI 卡片笔记。通过轻松无压力的记录,丰富多样的连接,科学智能的回顾和方便快捷的调用,帮助热爱思考的学习者,用每一次记录,助力未来。 可以到 reminds 官网了解更多:https://reminds-app.com
Overview

what is reminds MCP?

reminds MCP is a server designed for the reminds application, which is an AI card note-taking tool tailored for lifelong learners. It allows users to effortlessly record thoughts, create diverse connections, and intelligently review notes, aiding learners in their thinking process.

how to use reminds MCP?

To use reminds MCP, obtain your API Key from the reminds app under Settings -> Security -> Developer -> API Key. Then, configure it in your environment by setting up the MCP Tools in Cursor with the provided JSON configuration.

key features of reminds MCP?

  • Create fleeting notes in HTML format.
  • Retrieve content from fleeting notes.
  • Integration with the reminds application for seamless note-taking.

use cases of reminds MCP?

  1. Recording quick thoughts and ideas as fleeting notes.
  2. Accessing and managing notes efficiently through the reminds platform.
  3. Enhancing learning by connecting notes and reviewing them intelligently.

FAQ from reminds MCP?

  • What is a fleeting note?

A fleeting note is a temporary note that can be created and stored in HTML format for quick access.

  • How do I retrieve a fleeting note?

You can retrieve a fleeting note by using its ID through the provided API.

  • Is reminds MCP free to use?

Yes, reminds MCP is free to use, but you need an API key from the reminds app.

Server Config

{
  "mcpServers": {
    "reminds-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "reminds-mcp"
      ],
      "env": {
        "API_KEY": "$YOUR_API_KEY"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Jason Woo
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago
Alloy

2 days ago